alterios_discover_readonly

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

With no annotations present, the description must disclose behavioral traits. It only states 'safe read-only', which is minimal. It does not explain side effects, required permissions, or what 'probe' does (e.g., list available routes or test connectivity).

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 sentence, making it concise, but it is under-specified. Conciseness should not come at the expense of essential information. The structure lacks any meaningful details.

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 has two parameters and an output schema, the description should explain the purpose of parameters and the output format. It provides none of this, leaving the agent with insufficient context to use the tool correctly.

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 input schema has two parameters (profile, project_id) with 0% schema description coverage. The description provides no explanation of these parameters, their purpose, or how they affect the tool's behavior. This is a critical failure.

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 'Probe the known safe read-only Alterios REST routes' indicates a discovery action but is vague. It does not specify what probing entails or what information is returned. While it distinguishes itself as specific to read-only routes, it fails to clearly articulate the tool's primary function.

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 is provided on when to use this tool versus sibling tools like alterios_rest_get or alterios_call_readonly_service. The description lacks context about when to probe vs. call, leaving the agent without decision criteria.

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