add_session

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

Describes the action as manual addition, notes prerequisites (open command port), and mentions return type. Lacks detail on potential side effects, but given no annotations, it is fairly 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?

Well-structured with clear sections (use case, args, returns, prerequisites). The code example adds length but is helpful. Concise overall.

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?

Covers when to use, prerequisites, parameter defaults, and return type. Adequate for a two-parameter tool with an output schema.

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?

Parameters are described minimally as host and port, with defaults. Schema coverage is 0%, so description adds some value but doesn't provide deeper semantics like valid ranges or formats.

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?

Explicitly states it manually adds a Maya session at a specific host and port, distinguishing from auto-discovery. Clear verb-resource combination.

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?

Explicitly says to use when auto-discovery fails or for specific ports, and provides prerequisite steps with code example.

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