Get Person Roles

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds behavioral context beyond annotations by specifying that results include both current and historic roles, and by noting the dependency on a search_persons result. This is useful context, though it does not disclose pagination or output size limits.

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 two sentences, front-loads the purpose, and includes a specific usage trigger. Every word earns its place; there is no redundancy or filler.

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 simple read-only tool with an output schema present and rich annotations, the description is complete. It states the purpose, when to use it, and the key parameter source. The output schema handles return-value details, so no further description is needed.

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 50%: role_person_id has a description, but include_historic does not. The description compensates by explaining the source and usage of role_person_id ('Pass the role_person_id returned by search_persons') and implicitly covers include_historic with 'current and historic.' However, it does not explicitly mention the parameter name or how to disable historic results.

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 clearly states the tool's function: 'List all company roles (styreleder, daglig leder, etc.) held by a person, current and historic.' It uses a specific verb and resource, and explicitly distinguishes from sibling tools by specifying 'held by a person' and providing a sample user query.

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?

The description gives explicit when-to-use guidance: 'Use when the user asks 'what roles does Person A hold?'' It also provides a prerequisite and sourcing instruction: 'Pass the role_person_id returned by search_persons.' This tells the agent exactly when and how to invoke the tool.

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