probe_agent

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

The description discloses the side effect (updates state file) and return value (new state). Since no annotations are provided, it carries the full burden; however, it does not explain what 'probe' means in detail or mention permissions.

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 a single sentence with no unnecessary words. It is front-loaded with the main action. Could be slightly improved with structured bullet points.

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 tool with one parameter and no output schema, the description covers the action, side effect, and return value. However, lacking usage guidelines and parameter details, it is adequate but not comprehensive.

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 only parameter 'agent_id' has no schema description (0% coverage). The description adds minimal meaning beyond the parameter name and label, saying 'by id' but not clarifying format or constraints.

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 action (probe an agent), the specific operation (install-check and state update), and the return value (new state). This distinguishes it from siblings like 'list_agents' or 'get_state'.

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 guidance on when to use this tool versus alternatives like 'ping' or 'get_state'. The description implies it's for installation checking but doesn't specify prerequisites or exclusions.

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