wealthbox.tasks.get

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 only restates the parameter focus ('by id') and does not mention return format, error behavior, permissions, or any other operational traits, which is a significant gap for a tool that is otherwise opaque.

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 of four words, efficiently conveying the core purpose without redundancy. It is front-loaded and immediately understandable, achieving maximum conciseness.

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 tool with one parameter, no annotations, and no output schema, the description is extremely sparse. It does not describe the return value, behavior for invalid ids, or any usage context, leaving the agent with insufficient information to fully understand the tool's behavior. This is a minimal but incomplete description.

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?

Schema description coverage is 0%, so the description must compensate for the undocumented id parameter. However, it merely says 'by id', which adds no meaning beyond the schema's property name and type. No explanation of the id's meaning, format, or constraints is 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?

The description 'Get task by id' uses a specific verb and resource, clearly indicating a single-task retrieval. It distinguishes from sibling tools like tasks.list, tasks.create, tasks.update, and tasks.delete through the 'by id' qualifier, which implies a targeted fetch by identifier.

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?

There is no guidance on when to use this tool versus alternative retrieval or list operations. The description offers no context for selecting this tool, no prerequisites, and no exclusions, leaving the agent without direction on optimal usage.

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