mhangani_authorizations_list

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

With no annotations, the description carries full burden. It states the action 'List' and scope 'all recorded,' which implies a non-mutating operation, but it does not disclose any additional behavior such as whether the list is sorted, whether it includes revoked entries, or any access requirements.

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 concise sentence with no filler, getting straight to the point.

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 zero-parameter list tool with an output schema, the description adequately conveys the core operation. However, it leaves some contextual gaps (e.g., return format details, expected use cases) that are partly covered by the output schema, but a bit more elaboration on the scope would be useful.

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 tool has no parameters, so the schema provides full coverage trivially. The description doesn't need to explain any parameters, and the baseline for zero-parameter tools is acceptable.

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 the specific verb 'List' with a clear resource 'all recorded authorizations,' making its function unmistakable. It naturally differentiates from sibling tools like mhangani_authorize (create) and mhangani_authorizations_remove (delete) by being the read/list operation.

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 explicit when-to-use guidance or alternative comparisons are provided. The use case is implied by the tool's name and straightforward list operation, but it does not tell the agent when to choose this over other list tools or mention any exclusions.

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