getSenateProfile

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered by structured data. The description adds only the downstream purpose (ID lookup) and says nothing about pagination behavior, result volume, or what a profile record contains.

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, both front-loaded: what it does first, then the concrete use case. No filler, no restatement of the tool name.

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 read-only lookup with no output schema, the description covers what the tool returns ('profiles') and why you'd call it. It leaves pagination and profile field content implicit, which is a minor gap given the six optional filters.

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% with six self-documented filters (page, limit, active, senateID, latestParty, latestPosition), so the schema carries the parameter burden. The description adds no filtering guidance or format hints (e.g., valid party/position values) beyond what the schema already provides.

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 a clear verb+resource: 'Look up profiles of members of Congress with the FMP Senate Profiles API.' It names the backing API, which disambiguates it from sibling getHouseTrades* tools, though the phrase 'members of Congress' is broader than the tool's Senate-only scope and overlaps conceptually with the House 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?

Explicitly routes the agent: 'Use it to find a member's ID for the trade and net worth tools,' linking it to siblings like getSenateTradesById and getSenateNetWorth. There is no when-not guidance (e.g., vs. getSenatePositions), but the primary use case is stated outright.

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