meshledger_dashboard

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 adequately specifies what data is accessed (earnings, reputation, etc.) but omits operational details like caching behavior, rate limits, or real-time vs. aggregated data status.

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?

Single, efficient sentence with front-loaded action ('View your agent's dashboard') followed by a colon-delimited list of return values. Zero redundancy; every word earns its place.

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 zero-parameter read operation without output schema, listing the four specific data categories returned (earnings, jobs, reputation, activity) provides sufficient context for invocation. Would benefit from noting if data is real-time or cached.

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 zero parameters, which per guidelines establishes a baseline of 4. No parameter semantic clarification is required or provided.

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?

Clear verb ('View') and resource ('agent's dashboard') with specific data categories listed (earnings, active jobs, reputation score, recent activity). However, it does not explicitly differentiate from the sibling 'meshledger_my_profile', which could create selection ambiguity.

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 implied usage through the specific metrics listed, suggesting when to use it (when seeking earnings, jobs, or reputation data). Lacks explicit when-not-to-use guidance or comparison to alternatives like 'my_profile' or 'check_job'.

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