mgmt_grant_get

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

No annotations are provided, so the description must carry the full behavioral burden. 'Get grant for user' implies a read operation but does not disclose permissions, response format, side effects, or failure behavior. This is minimal at best.

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 very short, but it is under-specified rather than efficiently structured. The documentation URL is not explained and does not contribute actionable guidance, while the main sentence largely restates the tool name.

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 management API tool with no annotations and no output schema, this description is incomplete. It does not explain what a grant is, what the response contains, or how this call differs from the many related grant and counter tools in the sibling list.

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 description coverage is 100%, with 'counterId' and 'user_login' already documented in the input schema. The description adds no additional parameter meaning beyond the schema, so the baseline of 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 states a specific verb and resource: 'Get grant for user' indicates retrieval of a grant tied to a user. It is clear enough as an operation, though it does not explicitly distinguish itself from siblings like mgmt_grants_list or mgmt_my_grant_get.

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 given for when to use this tool versus alternatives. An agent cannot tell whether to call this, mgmt_grants_list, or mgmt_my_grant_get based on the description alone; the usage context is only weakly implied by the word 'get'.

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