Get Person Assignments

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description's mention of pagination and metadata adds some value but does not substantially increase behavioral transparency beyond the annotations. 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?

The description is a mix of useful information and redundancy (e.g., 'Resource Planning records' repeated). It includes endpoint details which may be helpful, but could be more concise. It is adequately structured but not exemplary.

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?

Despite having no output schema, the description only states it returns a paginated JSON array with pagination metadata, without detailing the fields of each assignment record. For a tool with 6 input parameters and no output schema, this is insufficient to understand the return data structure.

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 100% coverage with descriptions for all 6 parameters. The description reiterates required parameters and identifies URL path vs query string, but adds little semantic nuance beyond the schema. Baseline 3 is appropriate.

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 Resource Planning Assignment data for a given company and person, but it also mentions 'full details of a specific Resource Planning records by its identifier', which is misleading since the tool uses person_id and date range, not a single assignment identifier. The purpose is somewhat clear but has inconsistency.

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 only says 'Use this to fetch...' without providing any guidance on when to use this tool versus alternatives (e.g., get_current_company_assignments). There is no mention of when not to use it or prerequisites, so usage context is minimal.

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