List agreements

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so safety profile is known. Description adds that results are paginated, filterable, and sortable, and that only summaries are returned. No contradictions.

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 sentences, no wasted words. Front-loaded with the primary action and immediately clarifies what the tool returns. Every sentence adds essential information.

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?

With 10 parameters and no output schema, the description covers the main capabilities (pagination, filtering, sorting, scope). Could be improved by noting that results are paginated via cursor, but it already mentions cursor and limit. Pointing to get_agreement for full details is helpful. Good overall.

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 baseline is 3. Description adds value by grouping parameters into pagination, filtering, and sorting, and by mentioning that cursor and limit are for pagination, chain and state for filtering. This helps the agent understand how to combine parameters.

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 'Lists agreement summaries visible to the current API key' with a specific verb and resource. Explicitly distinguishes from sibling 'get_agreement' by noting that this returns summaries only, while the sibling returns the full record.

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?

Clearly indicates when to use (for listing summaries) and explicitly references 'get_agreement' for full records. Does not provide explicit 'when not to use' scenarios but the context is clear enough.

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