Get A List Of Possible RFI Managers For An RFI

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

Annotations already provide readOnlyHint=true and idempotentHint=true. Description adds pagination info and API endpoint, but inaccurately states it returns 'RFI records' instead of 'potential RFI managers', which misrepresents the output behavior.

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 5 sentences long. The first sentence is clear, but the second sentence is contradictory and wastes space. Pagination and API info are useful but could be condensed. Adequate but not concise.

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?

Without an output schema, the description should clarify the return structure. It says 'returns a paginated JSON array of RFI records', but the tool is about managers, not RFI records. This inaccuracy and lack of detail on item properties make it incomplete.

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 already documents all three parameters. The description only reiterates pagination usage without adding new meaning, meeting the baseline.

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 first sentence states the correct purpose (list possible RFI managers), but the second sentence contradicts it by claiming the tool fetches 'full details of a specific RFI records'. This inconsistency obscures the true function.

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?

No guidance on when to use this tool versus alternatives like 'get_a_list_of_possible_assignees_for_an_rfi' or 'list_available_rfi_rfi_manager_filter_options'. No when-not-to-use or prerequisite information.

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