nape_summary

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

With no annotations, the description relies entirely on itself. It states it returns data but does not disclose read-only nature or any side effects. The behavior is implied as a query, but explicit confirmation of no mutations would improve clarity.

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 efficient sentences: the first states functionality, the second provides usage guidance. No redundant information. Front-loaded with core purpose.

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 simple query tool with one optional parameter and no output schema, the description fully covers what it does, how to use it, and what it returns. No gaps remain.

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% for the single optional parameter, and the description's instruction mirrors the schema description. No additional meaning is added, so baseline 3 applies.

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 the tool returns honk counts grouped by four specific levels for a session or all sessions. The verb 'Return' and resource 'honk counts by level' are precise, and it implicitly distinguishes from siblings like nape_honks which provide raw data.

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?

Provides explicit context: 'Use this for a quick posture check.' Also gives usage instruction for the session_id parameter: 'Omit session_id for an all-session total.' However, it does not mention alternatives or when not to use, leaving some ambiguity against siblings.

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