Get Project Incident Configuration

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

Annotations already provide strong safety hints. The description adds that it returns a paginated array and mentions pagination metadata, though 'array of Incidents' seems inaccurate for a configuration endpoint. No contradiction with 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?

Mostly concise with two core sentences plus implementation details. Some redundancy in explaining pagination, but overall efficient for the content length.

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?

No output schema, so description should explain return format. It claims 'paginated JSON array of Incidents' but that may be wrong for a configuration endpoint. Adequate for simple parameters but lacks accuracy.

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 all three parameters with descriptions. The description adds context that page/per_page control pagination and project_id is required, but this doesn't significantly exceed schema documentation.

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 states it returns 'Incident configuration values', but then says 'fetch the full details of a specific Incidents by its identifier,' which is inconsistent. The endpoint and tool name suggest configuration, not individual incidents. This ambiguity detracts from clarity.

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 siblings like 'show_incident' or 'list_incidents'. The description implies it retrieves incident details, which may lead to incorrect selection.

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