getSenateNetWorth

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

Annotations already declare readOnlyHint=true, openWorldHint=true and idempotentHint=true, so the safety profile is covered. The description adds only the 'reported' nuance and the upstream API name, saying nothing about pagination behavior, result ordering, or that senateID must be an FMP-issued identifier.

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?

A single front-loaded sentence with the verb and resource first. The trailing 'with the FMP Senate Net Worth API' is mildly redundant naming that earns little, but the description is not bloated.

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 carries some burden for explaining what 'net worth records' contains (asset/liability ranges, filing dates), and it does not. Combined with the missing sibling differentiation against getSenateNetWorthAggregated, it is adequate but has clear gaps.

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 senateID, page and limit are all documented in the schema itself. The description adds no parameter-level meaning, which is acceptable given the schema does the heavy lifting, but it also does not clarify paging defaults for a paginated endpoint.

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 specific verb (Retrieve) and resource (reported net worth records of a member of Congress), so the agent knows exactly what data comes back. It does not, however, distinguish itself from the close sibling getSenateNetWorthAggregated, leaving the per-member vs. aggregate distinction unstated.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as getSenateNetWorthAggregated or getSenateProfile. The agent must infer from the name alone that this is the single-member lookup.

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