reply_invitation

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'Returns success status' and includes a 'WARNING: Uses unofficial API', which adds important context about reliability and potential risks. However, it lacks details on permissions, rate limits, or error handling, leaving gaps for a mutation tool.

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 well-structured and front-loaded with the core purpose, followed by parameter details and warnings. It uses bullet-like formatting for clarity but includes a redundant 'Args:' header that could be omitted for brevity without losing information.

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 tool's complexity (mutation with 3 parameters), no annotations, and an output schema present (implied by 'Returns success status'), the description is fairly complete. It covers purpose, parameters, and behavioral warnings, though it could benefit from more detail on error cases or side effects to achieve full completeness.

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 0%, so the description must compensate. It explains each parameter's purpose and source ('from get_invitations results') and specifies valid values for 'action' ('accept' or 'reject'), adding significant meaning beyond the bare schema. The default value for 'action' is noted in the schema but not in the description, slightly reducing the score.

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's purpose with specific verbs ('accept or reject') and resource ('a connection invitation'), distinguishing it from sibling tools like 'send_connection_request' or 'get_invitations'. It precisely defines the action without being tautological.

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 clear context by referencing 'get_invitations results' for parameter values, indicating when to use this tool (after retrieving invitations). However, it does not explicitly state when not to use it or name alternatives among siblings, such as 'send_connection_request' for initiating connections.

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