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

Annotations already mark the call as read-only, idempotent, and non-destructive, and the description adds valuable behavior beyond that: caching up to an hour, not-found errors for unknown ids, and the fact that an unauthorized call returns setup steps instead of data. No contradiction with annotations.

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 dense but every clause earns its place: return contents, usage context, sibling routing, error behavior, auth, and caching. It is front-loaded with the main resource and use case before moving into operational details.

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?

There is no output schema, but the description fully compensates by enumerating every return component, the data limit, the error case, the auth requirement, and the cache policy. An agent has everything needed to call and interpret this tool correctly.

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% and the single member_id parameter is already documented in the schema. The description adds meaning by telling the agent where to find this id, such as from search_members or any coldpine.io/politicians URL, which improves selection and invocation confidence.

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 the exact resource (one member of Congress) and enumerates the returned components: profile, aggregate stats, recent trades, transaction reports, and sample scored trade. It also gives a direct use case, 'what has this member been trading', which distinguishes it from sibling tools like list_transactions and get_filing.

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?

It explicitly tells the agent to obtain member_id from search_members first, and directs it to list_transactions when more than 20 trades are needed. It also covers authentication requirements and error behavior, so the when-to-use and alternatives are unambiguous.

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