getComponentChanges

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves 'recent changes' but doesn't specify what constitutes 'recent' (timeframe, limit), the format of returned changes, whether it's read-only (implied but not explicit), or any authentication/rate limit considerations. For a tool with no annotation coverage, this leaves significant behavioral gaps.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, with zero wasted content. Every word earns its place by conveying essential information about the tool's function.

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 complexity of a changes retrieval tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'changes' entail (e.g., edits, additions, deletions), the return format, pagination, or error handling. For a tool that likely returns structured change data, more context is needed to guide the agent effectively.

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 both parameters ('projectSlug', 'componentSlug') clearly documented in the schema. The description adds no additional parameter semantics beyond implying the tool operates on a component within a project. Since the schema already fully describes the parameters, the baseline score of 3 is appropriate—the description doesn't enhance or contradict the schema.

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 action ('Get recent changes') and target resource ('for a specific component'), which provides a specific verb+resource combination. However, it doesn't distinguish this tool from similar siblings like 'getProjectChanges' or 'listRecentChanges', which likely retrieve changes at different scopes. The purpose is clear but lacks sibling differentiation.

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 provides no guidance on when to use this tool versus alternatives. With siblings like 'getProjectChanges' and 'listRecentChanges' available, the agent has no indication whether this tool is for component-specific changes, project-wide changes, or unfiltered changes. There's no mention of prerequisites, exclusions, or comparative context.

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