Get HP company info

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It's clearly a read-only fetch operation (safe), which is a positive signal, but the description doesn't disclose anything beyond that—no mention of what the profile includes, whether it's static/cached, authentication needs, or error behaviors. For a tool with zero annotation coverage, more behavioral context would be expected.

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 concise sentence that fully states its purpose. It's appropriately brief for a zero-parameter tool. Minor demerit: it doesn't use the full 1-2 sentences it could afford to add behavioral or return context.

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-only fetch tool with no output schema, the description is relatively complete. However, it doesn't describe the return value or content scope (what fields the company profile contains). With no output schema and no annotations, some indication of what 'company profile' encompasses would improve completeness. It's adequate but minimal.

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 tool has 0 parameters, and schema coverage is 100% (empty schema), so there are no parameter semantics to explain. The baseline 4 for 0-param tools applies—nothing further is needed since there's nothing to document.

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 'Fetch the company (会社情報) profile from the HP' clearly states the action (fetch) and resource (company profile). It distinguishes reasonably from siblings get_news and get_news_detail, which target news content. Slight weakness: it doesn't name the destination company in the title/description explicitly beyond the function name, and 'HP' is ambiguous (could be Hewlett-Packard or homepage).

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?

The description indicates this fetches company profile info, which is distinct from news-related siblings by context. However, there's no explicit when-to-use guidance or exclusions stated. The implied context (company info vs news) is clear enough to select it, but no explicit alternatives are mentioned.

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