ACC.MCP

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 effectively describes key behaviors: browser interaction, token caching, auto-refresh, and persistence until logout. It could improve by mentioning error handling or timeout details, but covers the essential workflow clearly.

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 efficiently structured in three sentences: first explains the action and browser interaction, second covers token management and usage context, third clarifies scope determination. Every sentence adds value with zero redundant 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?

For a 0-parameter authentication tool with no annotations or output schema, the description provides comprehensive context about the OAuth flow, token management, and integration with other tools. It could mention potential errors or prerequisites, but covers the core functionality adequately.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately explains the OAuth scope is determined by configuration rather than parameters, adding useful context beyond the empty schema.

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 specific action ('Start a 3‑legged OAuth login for APS'), the resource ('user context'), and the mechanism ('Opens the user's browser to the Autodesk sign‑in page'). It distinguishes from sibling tools like aps_logout by describing the initiation of authentication rather than termination.

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 states when to use this tool ('All subsequent API calls use the 3LO token... until aps_logout is called') and provides clear context about the OAuth scope being determined by user configuration. It distinguishes from alternatives by focusing on user-context login without mentioning other authentication methods.

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