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

No annotations are provided, so behavioral disclosure falls entirely on the description. It transparently describes what data is returned, including the '20 most recent disclosed trades' and 'one sample scored trade the public page shows,' but it does not mention side effects, permissions, data freshness, or rate limits. The read-only nature is only implied by the name and content.

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 dense sentence that front-loads the core scope ('One member of Congress') and then efficiently lists specific return components. It is compact but slightly run-on, with several parenthetical elaborations packed into one clause.

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 no output schema, the description is the primary source of return-value information. It covers the major components an agent would need to know about: profile, stats, recent trades, filing links, PTRs, and a sample scored trade. It does not describe formatting or error behavior, but it is sufficiently complete for a simple get-by-id tool.

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?

The schema fully documents the only parameter, member_id, including its source and format. The description adds no parameter-level meaning, but schema coverage is 100%, so the baseline of 3 applies.

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 tool returns data for exactly one member of Congress and enumerates specific contents: profile, aggregate trading statistics, 20 recent trades with filing links, recent Periodic Transaction Reports, and a sample scored trade. This clearly distinguishes it from sibling tools like search_members or list_transactions.

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?

Usage is implied through 'One member of Congress' and the detailed list of returned data, but there is no explicit guidance about when to use this instead of siblings such as get_filing, list_transactions, or search_members. The schema does mention where to obtain member_id, which helps, but the description itself does not provide alternatives or exclusions.

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