cache_get_proposal

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

Describes the main action and output (includes audit trail), but does not disclose idempotency, side effects, or error behavior. Since no annotations are provided, the description carries full burden but remains minimal.

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?

Single sentence, no redundancy, front-loaded with key information. Efficient and to the point.

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?

Adequate for a simple fetch tool with one parameter, but could benefit from mentioning return format, error handling, or prerequisites. No output schema increases the need for such details.

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 covers the single required parameter with description, making the description's value additive only by mentioning the audit trail in the return. Baseline 3 as schema coverage is 100%.

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?

Clearly states the tool fetches a single cache proposal by id and includes its audit trail. Distinguishes from sibling list tools like cache_list and cache_list_pending_proposals.

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?

Implies usage for fetching a specific proposal, but lacks explicit guidance on when to use versus alternatives like cache_list or cache_propose_* tools. No when-not or alternative references.

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