disconnect-strava

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

With no annotations, the description carries the full transparency burden. It explicitly discloses the key side effect: 'remove stored credentials.' This goes beyond the name and informs the agent of the security-relevant action. It doesn't detail irreversibility or effects on other services, but for a zero-parameter tool this is adequate and notably transparent.

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, each earning its place: the first states the action, the second states when to use it. Front-loaded and free of filler. Excellent structure.

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?

For a simple action tool with no parameters and no output schema, the description is complete: it covers what, why, when, and the side effect. Sibling tools help disambiguate, and the description is self-sufficient. No gaps remain.

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?

The tool has zero parameters, so the baseline is 4. The description adds no parameter-specific information because none is needed. It appropriately focuses on the action and usage context, which is all that matters here.

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 uses a specific verb ('Disconnect') and identifies the resource ('your Strava account') plus additional detail ('remove stored credentials'). It clearly distinguishes this tool from siblings like connect-strava and check-strava-connection, which serve different purposes.

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?

Provides explicit guidance: 'Use this when the user wants to logout, disconnect, or remove their Strava connection.' This clearly states the intended use case. However, it lacks explicit 'when not to use' or alternative tool references, so it falls slightly short of a 5.

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