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

No annotations are present, so the description must fully disclose behavioral traits. It only states the action (resolve an id to descriptor) with no mention of side effects, required permissions, or what 'descriptor' means. The lack of detail makes it hard for the agent to anticipate results or safety.

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 sentence that is front-loaded with the verb and resource. However, it is too minimal; conciseness should not come at the expense of completeness. It earns a 3 for structure but lacks substance.

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?

Given the low complexity (one parameter, no output schema), the description should provide enough context for an agent to use it correctly. It does not explain what a capability descriptor is, how it is structured, or how to get the id (e.g., from list_capabilities). The description is incomplete.

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%, meaning the input schema provides no parameter descriptions. The tool description does not add any meaning beyond the parameter name 'id'. The agent is left to guess what a capability id is or how to obtain it.

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 states a specific verb 'Resolve' and resource 'capability id to its descriptor', making the core purpose clear. It implies retrieving a single descriptor by ID, which distinguishes it from siblings like list_capabilities that return all capabilities. However, it does not explicitly differentiate from search or get_example.

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?

No guidance is provided on when to use this tool versus alternatives such as list_capabilities (for browsing all capabilities) or search (for finding capabilities by other criteria). The agent is given no help in tool selection.

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