tcdb_card

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

Indicates read-only operation by describing 'Fetches a public TCDB card page', but lacks details on rate limits, authentication (likely none), or error handling. No annotations to demand additional context.

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?

Two sentences with no redundancy. Front-loaded with action and purpose, then lists output types. Every sentence earns its place.

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?

Describes return types (metadata, images, tags, set references) compensating for absent output schema. Lacks mention of error cases or single-result guarantee, but sufficient for a simple retrieval tool.

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 covers all 4 parameters with descriptions (url, path, set_id, card_id). Description adds no new parameter-specific information beyond the output types, so 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?

Clearly states action 'Get TCDB card detail' and specifies it fetches a public card page returning normalized metadata, image links, tags, and parent set references. Distinct from sibling tools like tcdb_set or tcdb_person.

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 on when to use this tool versus alternatives like tcdb_set or tcdb_search. Does not specify prerequisites or typical use cases.

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