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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which covers the read-only safety profile. The description adds that reviewed and unreviewed subjects are both included and emphasizes reuse over duplicate creation, but it stays close to the annotation-provided read-only semantics and doesn't address other consequences like empty results.

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 concise and front-loaded with the most important use case. Every sentence contributes, though 'before declaring a new one' and 'instead of creating a duplicate' repeat the same core idea, which prevents a perfect conciseness score.

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?

This is a straightforward look-up tool and the description explains its purpose and when to call it, which is good. However, there is no output schema, and the description does not mention what happens when no match is found or which identifier returns enough results. It is adequate, but there are clear gaps.

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?

With 0% schema description coverage, the description carries heavy weight here. It usefully maps many parameters (stable type, canonical key, name, authoritative identifier value), but it leaves identifier_key and limit undocumented and does not clarify which combination of parameters should be supplied. Partial compensation for the schema gap, not complete.

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 resolves/looks up an existing subject instead of creating a new one, which is a concrete verb and resource. It also distinguishes this tool from declaring/creating a subject, so an agent immediately knows its role.

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 explicitly tells the agent when to use this tool: before adding a collection subject, so an existing subject_id and canonical_key can be reused instead of creating a duplicate. It lacks explicit when-not-to-use instructions or named alternatives, but the intended use case is clear.

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