sap_get_agent_stats

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

Without annotations, the description should disclose behavioral traits. It fails to state that the tool is read-only, idempotent, or safe to call multiple times. It only implies a fetch operation but does not confirm no side effects.

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 very short and front-loaded. It wastes no words, but could be more informative without becoming overly verbose. It earns a 4 for efficiency.

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?

The description is too minimal given the lack of output schema and annotations. It does not explain what 'stats' means, the format of the return value, or any constraints like time range or aggregation. A more complete description would aid agent understanding.

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 already provides a good description for the single parameter ('Agent PDA (base58) to fetch stats for'). The description adds no additional meaning. Since schema coverage is 100%, baseline is 3.

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 ('Fetch') and resource ('agent stats') and specifies the input parameter ('by agent PDA'). It distinguishes itself from similar tools like 'sap_get_agent' and 'sap_get_agent_profile' by mentioning 'stats' specifically.

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 is provided on when to use this tool versus alternatives. The description does not explain why one would choose this over other fetch tools like 'sap_get_agent' or 'sap_get_agent_profile', nor does it mention any prerequisites or context.

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