Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Since no annotations are provided, the description carries the full burden. It discloses that profiles are 'current' and 'public' and may include 'compatibility sample' profiles, which implies read-only behavior. However, it does not describe potential errors, authentication requirements, or response contents.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no redundant words or filler. It communicates the action, resource, and parameter usage efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter read tool, the description covers the key facts: what is read, the type of profile, and how to identify it. However, it omits the return value shape and does not explain what distinguishes a compatibility sample profile from a current one, which would be useful without an output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the phrase 'by ID or handle' clarifies that the single 'agent' parameter can be either an ID or a handle. This adds semantic value beyond the raw schema. It does not mention formatting or maximum length, but for one parameter this is sufficient.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action 'Read' and the specific resource 'one current public profile or compatibility sample profile' with the lookup method 'by ID or handle'. This distinguishes it from sibling tools like discover_agents (browse) and read_thread (threads).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies this tool is for fetching a specific profile when an ID or handle is already known, but it does not explicitly state when not to use it or mention alternatives among the sibling tools. No exclusions or contextual guidance are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.