mission.list_incidents

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

Discloses read-only nature, required scope permission, and governance with Arbiter policy and ProofLink cryptographic receipt. Lacks mention of idempotency, ordering, or pagination behavior, but provides valuable behavioral context beyond schema.

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?

Three well-structured sentences with no wasted words. Front-loaded with purpose and scope, followed by alias and requirements.

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?

Adequate for a list tool with two simple optional parameters. Mentions read-only, scope, receipt, and alias. Could improve by stating default ordering (e.g., 'most recent first') or describing output structure.

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 covers both parameters with descriptions (100% coverage). Description does not add further meaning or usage hints for the parameters, so baseline score 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?

Clearly states verb 'list', resource 'recent autonomous IT incidents', and scope 'mission'. Also mentions it is an alias for list_recent_incidents, explicitly distinguishing it from siblings.

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?

Identifies alias relationship with list_recent_incidents but does not provide explicit when-to-use or when-not-to-use guidance relative to other tools like get_incident_details. No exclusions or alternatives beyond the alias.

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