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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds meaningful behavioral context beyond those annotations by stating that the tool does not connect to a server or grant authority, which helps an agent understand side-effect and permission implications. This is valuable added transparency with no contradiction.

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 with no filler. The primary purpose is front-loaded, and the behavioral caveat is a single useful second sentence. Every word 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 one-parameter, read-only, idempotent tool with a detailed input schema and an output schema, the description is mostly adequate. It lacks usage guidance and deeper parameter semantics, but the combination of annotations, schema, and description covers the core operational and safety aspects.

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%, so the description carries the burden of explaining the 'tools' parameter. It only refers obliquely to 'submitted MCP tool declarations' and does not describe the array structure, required 'name' field, or annotation object expectations. Some semantic value is present, but it does not meaningfully compensate for the lack of schema descriptions.

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 uses specific verbs ('Inventory', 'flag') and a clear resource ('submitted MCP tool declarations'), making the tool's purpose unambiguous. It does not explicitly differentiate from sibling tools like check_evidence_inventory, but the subject matter is distinct enough that an agent can infer its role.

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 gives no guidance on when to use this tool versus siblings or when to choose an alternative. The sentence 'This does not connect to a server or grant authority' clarifies limitations but not usage context, so the agent is left without selection criteria.

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