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

Annotations already declare readOnlyHint=true, and the description adds meaningful context beyond that: it states the return includes JSON Schema and rowVersion, and it flags the scope restriction for includeUsedBy (project-only). It also implies a safe read operation, consistent with the read-only annotation.

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 two sentences with zero redundancy. The core purpose is front-loaded, followed by scope and the optional flag behavior. Every clause adds value and is easy to scan.

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 read-only get with three fully documented parameters and no output schema, the description covers the essential behaviors: what is returned, scope options, and the includeUsedBy limitation. The practical tip about deleting adds completeness without overburdening.

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 100%, so all parameters are already described in the schema. The description reinforces the default values and adds the 'before deleting' hint, but does not introduce new semantic meaning beyond what the schema provides. Baseline 3 is appropriate given the high coverage.

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 tool retrieves one shared schema including its JSON Schema and rowVersion, distinguishing it from listing tools like list_shared_schemas. The inclusion of scope and includeUsedBy parameters clarifies the exact resource and optional behaviors.

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 provides clear context for when to use this tool (to fetch a single schema with full details) and gives explicit guidance on using includeUsedBy before deleting a schema. It does not explicitly mention alternatives, but the 'get' vs 'list' distinction and the practical tip are sufficient for most use cases.

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