get_contact_topics

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

No annotations provided, so description carries full burden. It states the operation (list) and data returned (effective state), but lacks details on side effects, rate limits, authentication, or data volume. It does not explicitly label the tool as read-only.

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?

Single sentence that is clear, front-loaded, and concise. Every word adds value without redundancy.

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?

Tool has 2 params, no output schema, no annotations. Description explains what it does but does not specify return format or possible values for effective state (e.g., subscribed/unsubscribed). Adequate but could be more complete for agent understanding.

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 coverage is 100%, so baseline is 3. Description adds semantic value beyond schema by explaining 'effective subscription state' as 'their explicit choice, else the topic's default', clarifying the meaning of the returned data. This justifies a score of 4.

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?

Description clearly states it lists every topic of the sender for a specific contact, showing the effective subscription state (explicit choice or default). This specific verb+resource distinguishes it from siblings like list_topics (lists topics without contact state) and set_contact_topics (sets topics).

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 explicit guidance on when to use or when not to use. The description implies use for checking a contact's subscription state per topic, but does not mention alternatives or exclusions. Sibling tools like set_contact_topics or list_topics are not referenced.

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