list_grain_analyses

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds that it lists 'past' analyses, implying historical/completed ones, but does not disclose behaviors such as pagination, ordering, or limits. This is a minor addition beyond annotations.

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, efficient sentence: 'List past qualitative (GRAIN) analyses. Optionally filter by portfolio_id.' Every word is purposeful, and the key information is front-loaded.

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?

Given the tool's simplicity (one optional parameter, read-only annotation, output schema available), the description is complete. It clearly states what the tool does and the filter option, while the schema and annotations cover the rest.

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 description already fully covers the only parameter (portfolio_id) with 'Optional: filter by portfolio UUID'. The description merely restates this with 'Optionally filter by portfolio_id', adding no new semantic meaning. Baseline is 3 given 100% schema coverage.

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 a specific action ('List') and resource ('past qualitative (GRAIN) analyses'), and distinguishes it from sibling tools like get_grain_analysis or analyze_qualitative. It also mentions the optional portfolio_id filter, further clarifying the scope.

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?

The description implies this is for viewing existing analyses rather than creating or retrieving a single one, but it does not explicitly name alternatives or exclusions. The optional filter is noted, but no explicit 'when to use' or 'when not to use' guidance is provided.

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