athena_claim_list

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

No annotations provided, so description carries full burden. It discloses that it lists and optionally filters, but doesn't describe return format, side effects, or any constraints. Since it's a read-only list, the lack of any mention of safety or limits is a gap.

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?

One sentence, front-loaded, no filler. It is appropriately concise, though it could be slightly more informative without being verbose.

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 annotations or output schema, the description provides only minimal context. The cryptic 'Y', the meaning of enum values, and the behavior of the limit parameter are unaddressed, making it insufficient for an agent to fully understand the tool's behavior and output.

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 description explicitly identifies 'y' and 'status' as filter parameters, adding meaning to the schema. However, it doesn't explain the enum values for y or status, nor mention the limit parameter. With 0% schema coverage, the description only partially compensates.

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 uses a specific verb 'List' and resource 'claim authority heads', clearly naming the operation. It also mentions optional filtering, distinguishing it from claim mutation tools like athena_claim_challenge or athena_claim_promote, though the term 'authority heads' is somewhat cryptic.

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. It doesn't mention any exclusions or conditions, though the filtering options imply usage for listing claims with specific statuses. Missing explicit when-not-to-use.

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