congress_member_full_profile

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

Annotations already provide readOnlyHint=true, so the safety profile is known. The description adds valuable behavioral context by revealing the composite nature (3 endpoints in parallel), listing specific data categories returned (party history, terms, committees, photo, website, legislative activity). While it doesn't discuss rate limits or response structure, it goes well beyond the annotation baseline.

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 compact and front-loaded. The first sentence states the core value, the second paragraph gives explicit usage guidance, and the third gives contextual use cases. Every line earns its place without redundancy or fluff.

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 composite tool with no output schema, this description is remarkably complete: it explains the composite nature, enumerates return contents, provides usage alternatives, and connects to adjacent tools for accountability research. All key aspects (purpose, alternatives, data categories) are addressed for the tool's complexity.

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 100%, so the schema fully documents both parameters. The description does not add deeper parameter meaning beyond what the schema already includes, such as format or examples for bioguide_id and default behavior for bill_limit. It meets the baseline but doesn't exceed it.

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 clearly states the tool gets a complete member of Congress profile in one call, explicitly listing combined components (bio/details, sponsored and cosponsored legislation) and contrasting with individual sibling tools. This strongly distinguishes it from congress_member_details, congress_member_bills, and similar tools.

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?

Provides explicit guidance: 'Use this instead of calling congress_member_details + congress_member_bills (sponsored) + congress_member_bills (cosponsored) individually.' It also describes ideal use cases for accountability research and references related tools for cross-referencing, making both when-to-use and alternatives clear.

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