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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false). The description adds a genuinely useful behavioral note beyond them: 'Does not execute any instruction,' which tells the agent the returned content is data to be read, not commands to follow. It stops short of describing return format or size, so it loses a point there.

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?

Two short sentences, zero padding, with the core purpose front-loaded and the behavioral caveat as a compact follow-up. Every clause earns its place.

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 single-parameter read tool whose annotations already declare it safe and closed-world, the description covers purpose, which document types exist, and that content must not be executed. The only minor gap is that it says nothing about what the response looks like, though a 'read instructions' tool has a fairly self-evident text return.

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 coverage is 0%, so the description must carry the parameter meaning, and it does: 'quickstart, shared-workspace or contribution instructions' explains what each of the three enum values retrieves. The wording is a slight paraphrase of the enum ('governance' vs 'contribution'), but the mapping is easy to infer.

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?

States a specific verb (Read) and a specific resource (canonical quickstart/shared-workspace/contribution instructions), and the three document types map directly to the enum values. It does not explicitly name the siblings (exchange_discover, exchange_search, exchange_stats), but those are clearly different operations, so an agent can still separate them without opening schemas.

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 when to use it — when an agent needs canonical guidance for setup, workspace, or contribution policy — but gives no explicit when/when-not conditions and never references the sibling tools as alternatives. Usage is inferable rather than stated.

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